Systems and methods for managing merchandising card reminders

ABSTRACT

The disclosed embodiments provide systems, methods, and techniques for managing merchandising cards. A merchandising card may be, for example, a gift card, loyalty card, or the like. Consistent disclosed embodiments, a system for managing merchandising cards may include one or more memory devices storing instructions and one or more processors configured to acquire, from a device over a network, a plurality of locations associated with the device, the device locations being acquired at different instances in time within a predetermined period of time. Additionally, the one or more processors may be configured to calculate an overall merchant confidence rating for a merchant using the device locations. Further, the one or more processors may be configured to, based on the overall merchant confidence rating, determine that the merchant matches a merchant that is associated with merchandising card, and send a reminder a user of the device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of pending U.S. application Ser. No.15/832,449, filed Dec. 5, 2017, which is a continuation of U.S.application Ser. No. 15/823,089, filed Nov. 27, 2017. The contents ofwhich each prior application are expressly incorporated herein byreference.

TECHNICAL FIELD

The disclosed embodiments generally relate to systems and methods formanaging merchandising cards and, more particularly, to systems andmethods for managing merchandising card reminders.

BACKGROUND

Customers often rely on merchandising cards when buying goods orservices from various merchants. Merchandising cards may include, forexample, gift cards or loyalty cards. Customers may receive gift cardsas gifts or prefer to use reloadable pre-paid gift cards as a way tomanage spending. Customers may use loyalty cards, on the other hand, toobtain redeemable points or discounts from a merchant by buyingparticular a number or dollar amount of goods or services.

Due to the recent developments in technology, customers now have accessto mobile applications and other systems that allow them to keep trackof various merchandising cards. In some instances, customers may needmultiple applications to keep track of all the types of themerchandising cards that they have obtained.

Moreover, although these applications are available to customers,customers rarely use these applications when they visit merchants. Thus,customers often do not fully obtain the benefits of their merchandisingcards. For example, customers often have merchandising cards withnonzero balances, miss out on the opportunity to collect rewards points,or neglect to redeem benefits by using their collected rewards pointsbefore an expiration date. Moreover, merchants also do not often receivethe full marketing and financial benefits provided by the highutilization of merchandising cards.

Thus, a need exists to provide customers with more efficient ways tomanage merchandising cards and increase customer utilization ofmerchandising cards. In view of these and other shortcomings andproblems with managing merchandising cards, improved systems andtechniques for managing merchandising cards are desirable.

SUMMARY

In the following description, certain aspects and embodiments of thepresent disclosure will become evident. It should be understood that thedisclosure, in its broadest sense, could be practiced without having oneor more features of these aspects and embodiments. It should also beunderstood that these aspects and embodiments are merely exemplary.

The disclosed embodiments address disadvantages of existing systems byproviding novel systems, methods, and techniques for managingmerchandising cards and merchandising card reminders. Consistent withcertain disclosed embodiments, a system for managing a merchandisingcard reminder is provided. The system may include one or more memorydevices storing instructions and one or more processors. The one or moreprocessors may be configured to execute instructions to acquire, from adevice over a network, a plurality of device locations, the devicelocations being associated with the device and being acquired atdifferent instances in time. The one or more processors may also beconfigured to execute instructions to determine a geofence associatedwith a merchant location, the merchant location being associated with afirst merchant. Moreover, the one or more processors may be configuredto determine a first merchant confidence rating based on whether thedevice locations are within the geofence. The one or more processors mayalso be configured to determine whether the first merchant confidencerating is greater than or equal to a first threshold. If the firstmerchant confidence rating is greater than or equal to a firstthreshold, the one or more processors may be configured to acquire amerchant identifier associated with the merchant location; acquire aplurality of available merchant identifiers from the financial serviceprovider; and determine whether the first merchant identifier matches asecond merchant identifier in the available merchant identifiers, thefirst and available merchant identifiers being associated with amerchandising card of the user of the device. Furthermore, if the firstmerchant identifier matches a second merchant identifier in theavailable merchant identifiers, the one or more processors may beconfigured to send a notification to the user of the device indicatingthat the user is a holder of the associated merchandising card.

In addition, consistent with certain disclosed embodiments, a method isprovided for managing a merchandising card reminder. The method mayinclude the step of acquiring, from a device over a network, a pluralityof device locations, the device locations being associated with thedevice and being acquired at different instances in time. The method mayalso include the step of calculating a first merchant confidence ratingby: determining a geofence associated with a merchant location, themerchant location being associated with a first merchant; anddetermining the first merchant confidence rating based on whether thedevice locations are within the geofence for a predetermined period oftime. Further, the method may include the step of determining whetherthe first merchant confidence rating is greater than or equal to a firstthreshold. In response to determining that the first merchant confidencerating is greater than or equal to a first threshold, the method mayinclude the steps of acquiring a first merchant identifier associatedwith the merchant location; acquiring a plurality of available merchantidentifiers from the financial service provider; and determining whetherthe first merchant identifier matches a second merchant identifier inthe available merchant identifiers, the first and available merchantidentifiers being associated with a merchandising card of the user ofthe device. Further, in response to determining that the first merchantidentifier matches a second merchant identifier in the availablemerchant identifiers, the method may include the steps of sending anotification to the user of the device indicating that the user is aholder of the associated merchandising card.

Consistent with certain disclosed embodiments, a mobile device formanaging a merchandising card reminder is provided. The mobile devicemay include a memory device storing instructions and one or moreprocessors. The one or more processors may be configured to acquire aplurality of mobile device locations, the device locations beingacquired at different instances in time. The one or more processors mayalso be configured to calculate an overall merchant confidence ratingbased on the device locations over a predetermined period of time.Further, the one or more processors may be configured to determinewhether the overall merchant confidence rating is greater than a firstthreshold. If the overall merchant confidence rating is greater than orequal to a first threshold, the one or more processors may be configuredto acquire a merchant identifier associated with the merchant location;acquire a set of available merchant identifiers from the financialservice provider; and determine whether the first merchant identifiermatches a merchant identifier in the set of available merchantidentifiers, the first and set of available merchant identifiers beingassociated with a merchandising card of the user of the mobile device.Furthermore, if the first merchant identifier matches a second merchantidentifier in the available merchant identifiers, the one or moreprocessors may be configured to send a notification to the user of themobile device indicating that the user is a holder of the associatedmerchandising card.

Moreover, consistent with certain disclosed embodiments, a method isprovided for managing a merchandising card reminder. The method mayinclude the step of acquiring a plurality of device locations, thedevice locations being acquired at different instances in time andassociated with a mobile device. The method may also include the step ofcalculating an overall merchant confidence rating based on the devicelocations over a predetermined period of time. Moreover, the method mayinclude the step of determining whether the overall merchant confidencerating is greater than a first threshold. In response to determiningthat the overall merchant confidence rating is greater than or equal toa first threshold, the method may include the steps of acquiring a firstmerchant identifier associated with the merchant location; acquiring aset of available merchant identifiers from the financial serviceprovider; and determining whether the first merchant identifier matchesa merchant identifier in the set of available merchant identifiers, thefirst and set of available merchant identifiers being associated with amerchandising card of the user of the mobile device. Further, inresponse to determining that the first merchant identifier matches asecond merchant identifier in the set of available merchant identifiers,the method may include the steps of sending a notification to the userof a mobile device indicating that the user is a holder of theassociated merchandising card.

Consistent with certain disclosed embodiments, a system for managing amerchandising card reminder is provided. The system may include a memorystoring instructions and one or more processors. The one or moreprocessors may be configured to acquire from a device over a network, aplurality of device locations, the device locations being associatedwith a mobile device and being acquired at different instances in time.The one or more processors may also be configured to calculate anoverall merchant confidence rating based on the device locations over apredetermined period of time. Further, the one or more processors may beconfigured to determine whether the overall merchant confidence ratingis greater than a first threshold. If the overall merchant confidencerating is greater than or equal to a first threshold, the one or moreprocessors may be configured to acquire a merchant identifier associatedwith the merchant location; acquire a set of available merchantidentifiers from the financial service provider; and determine whetherthe first merchant identifier matches a merchant identifier in the setof available merchant identifiers, the first and set of availablemerchant identifiers being associated with a merchandising card of theuser of the mobile device. Furthermore, if the first merchant identifiermatches a merchant identifier in the set of available merchantidentifiers, the one or more processors may be configured to send anotification to the user of the mobile device indicating that the useris a holder of the associated merchandising card.

Aspects of the disclosed embodiments may also include a non-transitorytangible computer-readable medium that stores software instructionsthat, when executed by one or more processors, are configured for andcapable of performing and executing one or more of the methods,operations, and the like consistent with disclosed embodiments.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory only,and are not restrictive of the disclosed embodiments as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the description, serve to explain the disclosedembodiments. In the drawings:

FIG. 1 is a block diagram of an exemplary card management system,consistent with disclosed embodiments;

FIG. 2 is a block diagram of an exemplary computer system, consistentwith disclosed embodiments;

FIG. 3 is a flowchart of an exemplary process for managing merchandisingcards, consistent with disclosed embodiments;

FIG. 4 is a flowchart of an exemplary process for managing merchandisingcard reminders associated with a merchandising card, consistent withdisclosed embodiments;

FIG. 5 is a flowchart of an exemplary process for determining whether auser is located at a merchant location, consistent with disclosedembodiments;

FIG. 6 is a flowchart of an exemplary process for computing a merchantconfidence rating, consistent with disclosed embodiments; and

FIG. 7 is a flowchart of an exemplary process for determining whether amerchant, associated with a merchant location where the user is located,matches a merchant that is associated with a merchandising card,consistent with disclosed embodiments.

DETAILED DESCRIPTION

Generally, the disclosed embodiments are directed to systems and methodsfor managing merchandising card reminders. In particular, the systemsand methods may include techniques for managing merchandising cardreminders associated with a financial account.

The term “merchandising card” may refer to a gift card, a loyalty card,a rewards card, a discount card, or the like. In addition, amerchandising card may be a physical merchandising card, a digitalmerchandising card, or both. In some embodiments, a merchandising cardmay be associated with a particular merchant, that is, a particularmerchant may provide a merchandising card to a user (i.e., customer) foruse in a merchandising program. A merchandising program may be one or acombination of a gift card program, a loyalty card program, a rewardsprogram, a discount card program, a VIP program, or the like. A merchantmay offer one or more users (i.e. customers) the opportunity toparticipate in one or more merchandising program. In some embodiments,the merchant may give a user a merchandising card as a way toparticipate in the merchandising program. In some embodiments, themerchandising card may be associated with a particular merchandisingprogram.

A merchant may include any company, business, individual, or charitythat conducts any type of transactions. For example, a merchant may be aretailer, a financial service provider, an automotive dealer, a softwareprovider, or the like. In some embodiments, the merchant may sell anitem or service from a merchant location. This merchant location may bea physical location (i.e., brick and mortar location) or a virtual(online) location. Moreover, in some other embodiments, a customer maybe able to buy these items or services from the merchant by visiting themerchant location.

A user (i.e., customer) may be any entity that buys an item or servicefrom a merchant. In some embodiments, a customer may sign-up toparticipate in a merchandising program that is associated with one ormore particular merchants. To use and access the benefits of themerchandising program, a user may acquire a merchandising card from amerchant. In some embodiments, a user may use the merchandising card tobuy goods or services from the merchant. A user may also use themerchandising card to collect points or redeemable credit to acquirerewards based on the terms of the merchandising program. Throughout thisdisclosure, the terms user, customer, and consumer may be usedinterchangeably.

In some embodiments, customers may also have the ability to upload theirelectronic or physical merchandising card to a card management system,such as a card management system associated with a financial serviceprovider. In some embodiments, components of the card management systemmay be implemented in an application that is installed on a user'smobile device.

In certain embodiments, the card management system may acquire positioninformation (e.g., via global positioning system (GPS) coordinates) froma customer's device over a network. In some embodiments, the cardmanagement system may be implemented by a financial service provider, afinancial service provider device, a merchant device, a user device, orthe like, or any combination thereof. The card management system, insome embodiments, may calculate a merchant confidence rating (e.g.,high, medium, low, etc.) to determine whether the customer is locatedinside or in proximity to a physical location of a particular merchantfrom which the customer has received a merchandising card of thatmerchant. In some embodiments, if the card management system determinesthat the customer is located inside or in proximity to a physicallocation of a merchant and the customer has a merchandising card that isassociated with that merchant, the card management system may send anotification to the customer's device to notify the customer concerningsome aspect the merchandising card.

Reference will now be made in detail to exemplary embodiments, examplesof which are illustrated in the accompanying drawings and disclosedherein. Wherever convenient, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

FIG. 1 shows a block diagram of an exemplary card management system 100for managing merchandising cards, consistent with disclosed embodiments.The components and arrangements shown in FIG. 1 are not intended tolimit the disclosed embodiments, as the components used to implement thedisclosed processes and features may vary.

In accordance with disclosed embodiments, card management system 100 mayinclude a user device 110, a merchant device 120, a financial serviceprovider device 130, a wide-area network (WAN) 140, and a local network145. Other components known to one of ordinary skill in the art may beincluded in card management system 100 to gather, process, transmit,receive, acquire, and provide information used in conjunction with thedisclosed embodiments. In addition, card management system 100 mayfurther include other components that perform or assist in theperformance of one or more processes that are consistent with disclosedembodiments.

In some embodiments, card management system 100 may include one or moreuser devices 110. A customer may operate user device 110, which may be adesktop computer, a laptop, a tablet, a smartphone, a multifunctionalwatch, a pair of multifunctional glasses, a tracking device, or anysuitable device with computing capability. User device 110 may comprisea memory, a processor, and/or other specialized hardware that isconfigured to execute one or more methods of the disclosed embodiments.User device 110 may have an application installed thereon, which mayenable user device 110 to communicate with merchant device 120 and/orfinancial service provider device 130 via WAN 140 and/or local network145. Alternatively, user device 110 may connect to financial serviceprovider device 130 and/or merchant device 120 through use of webbrowser software.

User device 110 may allow a user to access information stored infinancial service provider device 130, such as, for example, financialinformation related to recent purchase transactions, financialdiscounts, financial statements, account information, merchandisingprogram information, merchandising card information, and/or the like.User device 110 may also include a GPS unit (not pictured). In someembodiments, user device 110 may use the GPS unit to acquire andtransmit the position information, such as the physical location of userdevice 110, to merchant device 120 and/or financial service providerdevice 130. An exemplary computer system consistent with user device 110is discussed in additional detail with respect to FIG. 2.

A user may operate user device 110 to perform one or more operationsconsistent with disclosed embodiments. In one aspect, a user may be acustomer of a financial service provider that may be associated withfinancial service provider device 130. For instance, a financial serviceprovider may maintain a financial service account (e.g., credit cardaccount) for the customer that the customer may use to purchase goodsand/or services online or at brick-and-mortar locations associated witha merchant. In another aspect, a user may also be a customer of amerchant that is associated with merchant device 120. For instance, auser may operate user device 110 to initiate purchase transactions witha merchant via merchant device 120 and receive communications associatedwith a merchandising card. Additionally, in certain embodiments, a usermay operate user device 110 to view a financial service account orfinancial statement provided by a financial service provider orfinancial service provider device 130.

Card management system 100 may also include one or more merchant devices120. Merchant device 120 may be a computing system that is associatedwith a merchant or other business entity such as a retailer, a grocerystore, a service provider (e.g., utilities, etc.), or any other type ofentity that provides goods and/or services that customers may purchase.While card management system 100 is shown in FIG. 1 with one merchantdevice 120, the disclosed embodiments may be implemented in a systemincluding two or more merchant devices 120 associated with any number ofunderlying business entities. Further, merchant device 120 is notlimited to conducting business in any particular industry or field.

Merchant device 120 may be associated with a merchant brick-and-mortarlocation that a user may physically visit to purchase goods and/orservices from a merchant. Such physical locations may include merchantdevices 120, which may include computing devices that perform financialservice transactions with customers (e.g., Point of Sale (POS)terminals, kiosks, etc.). Merchant device 120 may also include back-and/or front-end computing components that store data and executesoftware instructions to perform operations consistent with disclosedembodiments, such as computers that are operated by employees of themerchant (e.g., back-office systems, etc.). Merchant device 120 may alsobe associated with a merchant that provides goods and/or services viaknown online or e-commerce type of solutions. For example, such amerchant may sell goods via a website using known online or e-commercesystems and solutions to market, sell, and process online transactions.

In some embodiments, merchant device 120 may include one or more serversor other type of computing devices configured to execute softwareinstructions stored in memory to perform one or more processesconsistent with disclosed embodiments. For example, merchant device 120may include one or more memory devices storing data and softwareinstructions and one or more processors configured to use the data andexecute the software instructions to perform server-based functions andoperations known to those skilled in the art. In some embodiments,merchant device 120 may have an application installed thereon to performone or more processes that are consistent with disclosed embodiments.

In certain embodiments, merchant device 120 may further include serversthat are configured to execute stored software instructions to performoperations associated with a merchant, including processes associatedwith handling purchase transactions, generating transaction data,generating product data (e.g., SKU data) relating to purchasetransactions, etc. Merchant device 120 may include one or more serversthat may be a general-purpose computer, a mainframe computer, or anycombination of these components. In certain embodiments, merchant device120 (or a system including merchant device 120) may be configured as anapparatus, system, and the like based on the storage, execution, and/orimplementation of the software instructions that perform one or moreoperations consistent with disclosed embodiments. Merchant device 120may be standalone or part of a subsystem included in a larger system.For example, merchant device 120 may include distributed servers thatare remotely located and communicate over a network (e.g., WAN 140 orlocal network 145. An exemplary computer system consistent with merchantdevice 120 is discussed in additional detail with respect to FIG. 2.

In some embodiments, card management system 100 may also include one ormore financial service provider devices 130. Financial service providerdevice 130 may be a system associated with a financial service provider(not shown), such as a bank, a credit card company, a lender, brokeragefirm, or any other type of financial service entity that generates,provides, manages, maintains financial service accounts, managesmerchandising cards etc., for customers. Financial service providerdevice 130 may be one or more computing systems that are configured toexecute software instructions stored on one or more memory devices toperform one or more operations consistent with disclosed embodiments.For example, financial service provider device 130 may include memorydevices storing data and software instructions and processors configuredto use the data and execute the software instructions to performserver-based functions and operations known to those skilled in the art.Financial service provider device 130 may include one or moregeneral-purpose computers, mainframe computers, or any combination ofthese types of components. In some embodiments, financial serviceprovider device 130 may have an application installed thereon to performprocesses that are consistent with disclosed embodiments.

In certain embodiments, financial service provider device 130 may beconfigured as a particular apparatus, system, and the like based on thestorage, execution, and/or implementation of the software instructionsthat perform operations consistent with disclosed embodiments. Financialservice provider device 130 may be standalone, or it may be part of asubsystem included in a larger system. For example, financial serviceprovider device 130 may include distributed servers that are remotelylocated and communicate over a network (e.g., WAN 140 and/or localnetwork 145) or a dedicated network of a financial service provider. Anexemplary computing system consistent with financial service providerdevice 130 is discussed in additional detail with respect to FIG. 2,below.

Financial service provider device 130 may include or may access one ormore storage devices configured to store data and/or softwareinstructions used by one or more processors of financial serviceprovider device 130 to perform operations consistent with disclosedembodiments. For example, financial service provider device 130 mayinclude memory configured to store one or more software programs thatperform several functions when executed by a processor. The disclosedembodiments are not limited to separate programs or computers configuredto perform dedicated tasks. For example, financial service providerdevice 130 may include memory that stores a single program or multipleprograms. Additionally, financial service provider device 130 mayexecute one or more programs located remotely from financial serviceprovider device 130. For example, financial service provider device 130may access one or more remote programs stored in memory included with aremote component that, when executed, perform operations consistent withdisclosed embodiments. In certain aspects, financial service providerdevice 130 may include server software that generates, maintains, andprovides services associated with merchandising card management. Inother aspects, financial service provider device 130 may connectseparate servers or similar computing devices that generate, maintain,and provide services associated with financial data for a financialservice provider associated with financial service provider device 130.

WAN 140 may comprise any computer networking arrangement used toexchange data. For example, WAN 140 may be the Internet, a private datanetwork, a virtual private network (VPN) using a public network, and/orother suitable connections that enable the components of card managementsystem 100 to send and acquire information. WAN 140 may also include apublic switched telephone network (“PSTN”) and/or a wireless networksuch as a cellular network, wired Wide Area Network, Wi-Fi network, orother known wireless network (e.g., WiMAX) capable of bidirectional datatransmission.

Local network 145 may comprise any type of computer networkingarrangement used to exchange data in a localized area, such as Wi-Fibased on IEEE 802.11 standards, Bluetooth™, Ethernet, and other suitablenetwork protocols that enable components of card management system 100to interact with one another and to connect to WAN 140 for interactingwith components in system environment 100. In some embodiments, localnetwork 145 comprises a portion of WAN 140. In other embodiments,components of card management system 100 may communicate via WAN 140without a separate local network 145.

FIG. 2 shows a block diagram of an exemplary computing system 200illustrating a computing system configuration that may be associatedwith user device 110, merchant device 120, and/or financial serviceprovider device 130, consistent with disclosed embodiments. In someembodiments, computing system 200 may have one or more processors 210,one or more input/output (I/O) devices 220, and/or one or more memories230. In certain embodiments, computer system 200 may also be connectedto a database 240 and/or a cloud service 250.

In some embodiments, computing system 200 may take the form of a server,a general-purpose computer, a mainframe computer, a laptop, asmartphone, a mobile device, or any combination of these components. Incertain embodiments, computing system 200 (or a system includingcomputing system 200) may be configured as a particular apparatus,system, and the like based on the storage, execution, and/orimplementation of the software instructions that perform one or moreoperations consistent with disclosed embodiments. Computing system 200may be standalone, or it may be part of a subsystem included in a largersystem.

Processor 210 may include one or more known processing devices, such asa microprocessor from the Pentium™ or Xeon™ family manufactured byIntel™, the Turion™ family manufactured by AMD™, or any of variousprocessors manufactured by Sun Microsystems or other manufacturers.Processor 210 may constitute a single-core or multiple-core processorthat executes parallel processes simultaneously. For example, processor210 may be a single-core processor configured with virtual processingtechnologies. In certain embodiments, processor 210 may use logicalprocessors to simultaneously execute and control multiple processes.Processor 210 may implement virtual machine technologies, or other knowntechnologies to provide the ability to execute, control, run,manipulate, store, etc., multiple software processes, applications,programs, etc. In certain embodiments, processor 210 may include amultiple-core processor arrangement (e.g., dual, quad-core, etc.)configured to provide parallel processing functionalities to allowcomputing system 200 to execute multiple processes simultaneously. Oneof ordinary skill in the art would understand that other types ofprocessor arrangements could be implemented that provide for thecapabilities disclosed herein. The disclosed embodiments are not limitedto any type of processor(s) configured in computing system 200.

Memory 230 may include one or more storage devices configured to storedata and instructions used by processor 210 to perform functions relatedto the disclosed embodiments. For example, memory 230 may be configuredwith software instructions, such as program 236 that may performoperations when executed by processor 210. The disclosed embodiments arenot limited to separate programs or computers configured to performdedicated tasks. For example, memory 230 may include a single program236 that performs the functions of computing system 200, or program 236could comprise multiple programs. Additionally, processor 210 mayexecute one or more programs located remotely from computing system 200.For example, user device 110, merchant device 120, and/or financialservice provider device 130, may, via computing system 200 (or variantsthereof), access one or more remote programs that, when executed,perform functions related to certain disclosed embodiments. Processor210 may further execute one or more programs located in database 240and/or cloud service 250. In some embodiments, program 236 may be storedin an external storage device, such as at cloud service 250 locatedoutside of computing system 200, and processor 210 may execute program236 remotely.

Programs 236 executed by processor 210 may cause processor 210 toexecute one or more processes related to financial services provided tousers including, but not limited to, processing credit and debit cardtransactions, checking transactions, funding deposits and withdrawals,transferring money between financial accounts, lending loans, processingpayments for credit card and loan accounts, and managing merchandisingcards, which includes managing merchandising card reminders.

I/O device 220 may be one or more devices configured to allow data to beacquired and/or transmitted by computing system 200. I/O device 220 mayinclude one or more digital and/or analog communication devices thatallow computing system 200 to communicate with other machines anddevices, such as other components of card management system 100 shown inFIG. 1. For example, computing system 200 may include interfacecomponents that may provide interfaces to one or more input devices,such as keyboards, mouse devices, and the like, which may enablecomputing system 200 to acquire input from an operator of financialservice device 130 (FIG. 1).

Memory 230 may also store data that may reflect any type of informationin any format that the system may use to perform operations consistentwith disclosed embodiments. Memory 230 may store instructions to enableprocessor 210 to execute one or more applications, such as serverapplications, a merchandising card management application, networkcommunication processes, and any other type of application or software.Alternatively, the instructions, application programs, etc., may bestored in an external storage (not shown) in communication withcomputing system 200 via WAN 140 or any other suitable network. Memory230 may be a volatile or non-volatile, magnetic, semiconductor, tape,optical, removable, non-removable, or other type of storage device ortangible (i.e., non-transitory) computer-readable medium.

Memory 230 may include transaction data 232. Transaction data 232 mayinclude information related to purchasing transactions initiated by auser. For example, transaction data may include a user identifier and apurchase price. The user identifier may be a credit or debit cardnumber, an account number, or other means of identifying the userinitiating the purchase transaction. The purchase price may include anumber representing the total sale price of the purchase transactionand/or may include a list of the various items purchased from themerchant. In some embodiments, merchant device 120 may collect,generate, and provide transaction data relating to purchase transactionsinvolving a user to financial service provider device 130. In someembodiments, merchant device 120 may further provide product data (e.g.,SKU data) and transaction data relating to purchase transactionsinvolving a user to financial service provider device 130. Merchantdevice 120 may provide this information to financial service providerdevice 130 via WAN 140. In some embodiments, transaction data 232 may bestored in database 240 and/or cloud service 250 or in an externalstorage (not shown) in communication with computing system 200 via WAN140 or any other suitable network.

Memory 230 may further include client data 234. Client data 234 mayinclude information about particular customers of the financial serviceprovider. For example, client data 234 may include customers' accountinformation, debit or credit card information, history of purchasetransactions, financial statements, credit score, risk profile, and/ormerchandising card data. Client data 234 may further contain one or moreuser profiles associating the account information, debit or credit cardinformation, history of purchase transactions, financial statements,credit score, risk profile, and/or merchandising card information,including stored merchandising cards. When a user initiates a purchasetransaction, processor 210 may analyze client data 234 or user profilesbefore authorizing the purchase transaction on behalf of a user. In someembodiments, client data 234 may be stored in database 240 and/or cloudservice 250 or in an external storage (not shown) in communication withcomputing system 200 via WAN 140 or any other suitable network.

Processor 210 may analyze transaction data 232 in reference to clientdata 234. For example, processor 210 may analyze transaction data todetermine which client with information stored in client information 234is initiating the purchase transaction. Processor 210 may access theparticular user's client information to determine their accountinformation, debit or credit card information, history of purchasetransactions, financial statements, credit score, risk profile, and/ormerchandising card information.

Computing system 200 may also contain one or more databases 240. In someembodiments, computing system 200 may be communicatively connected todatabase 240 through WAN 140 and/or local network 145. Database 240 mayinclude one or more memory devices that store information and areaccessed and/or managed through computing system 200. By way of example,database 240 may include Oracle™ databases, Sybase™ databases, or otherrelational databases or non-relational databases, such as Hadoopsequence files, HBase, or Cassandra. The databases or other files mayinclude, for example, data and information related to the source anddestination of a network request, the data contained in the request,etc. Systems and methods of disclosed embodiments, however, are notlimited to separate databases. Database 240 may include computingcomponents (e.g., database management system, database server, etc.)configured to acquire and process requests for data stored in memorydevices of database(s) 240 and to provide data from database 240.

Computing system 200 may be communicatively connected to one or morecloud service(s) 250. In some embodiments, computing system 200 may becommunicatively connected to cloud service 250 through WAN 140 and/orlocal network 145. Cloud service 250 may include a physical and/orvirtual storage system associated with cloud storage for storing dataand providing access to data via a public network 145, such as theInternet. Cloud service 250 may include cloud services such as thoseoffered by, for example, Amazon®, Apple®, Cisco®, Citrix®, IBM®,Joyent®, Google®, Microsoft®, Rackspace®, Salesforce.com®, andVerizon®/Terremark®, or other types of cloud services accessible via WAN140. In some embodiments, cloud service 250 comprises multiple computersystems spanning multiple locations and having multiple databases ormultiple geographic locations associated with a single or multiple cloudstorage service(s). As used herein, cloud service 250 refers to physicaland virtual infrastructure associated with a single cloud storageservice and may manage and/or store data associated with managingmerchandising card reminders.

As discussed above, financial service device 130 may include at leastone computing system 200. Further, it should be understood thatvariations of computing system 200 may be used by other components ofcard management system 100, including merchant device 120 and userdevice 110. In some embodiments, computing system 200 may be a singleserver or may be configured as a distributed computer system includingmultiple servers or computers that interoperate to perform one or moreof the processes and functionalities associated with the disclosedembodiments.

FIG. 3 shows an exemplary process for managing merchandising cards,consistent with disclosed embodiments. In some embodiments, processor210 of, for example, financial service provider device 130 will executeinstructions encoded on a computer-readable storage medium to performsteps of the process for managing merchandising cards described by FIG.3. It should also be understood, however, that one or more steps ofprocess 300 may be implemented by other components of card managementsystem 100 (shown or not shown), including merchant device 120 and/oruser device 110.

At step 310, financial service provider device 130 may acquire user datarelating to a customer of a financial service provider. In someembodiments, financial service provider device 130 may acquire user dataover WAN 140 from, for example, user device 110. User data may beentered manually by the user into user device 110 by typing it on akeyboard or other input device (not shown). User data may also beentered automatically, for example, by scanning or swiping a credit ordebit card on user device 110 or merchant device 120, which may containuser data pertaining to the user or by taking a picture of a credit ordebit card using an application that may be installed on user device 110or merchant device 120.

Financial service provider device 130 may use the user data to identifyone or more customer accounts associated with the user (step 320). Forexample, financial service provider device 130 may compare user dataacquired from user device 110 or merchant device 120 with client data234 to identify one or more customer accounts associated with the user(using, e.g., a financial account identifier indicated in the userdata).

At step 330, financial service provider device 130 may acquiremerchandising card data associated with one or more merchandising cardsowned or held by a user. In some embodiments, merchandising card datamay include, for example, a merchant identifier identifying the merchantat which the merchandising card is redeemable and a value identifyingthe amount of credit on the merchandising card. In some embodiments,merchandising card data may include, for example, a number of points orvalue awarded, a number of points or value earned, a maximum or aminimum number of points or value that the merchandising card can hold,an expiration date that indicates when the number of points earned orawarded will expire, etc. Merchandising card data may, alternatively oradditionally, include a merchandising card identifier number, a serialnumber identifying the particular merchandising card for which data hasbeen acquired, etc. In some embodiments, merchandising card data may bestored and associated with stored merchant identifiers. Merchantidentifiers may include merchant names, merchant codes, merchantcategory codes, ticker symbols, or the like. In addition, merchantidentifiers may be stored in database 240 and/or cloud service 250.Merchant identifiers may be stored separately or with othermerchandising card data.

Merchandising card data may be acquired by financial service providerdevice 130 from, for example, user device 110 and/or merchant device120. For example, merchandising card data may be entered manually by theuser into user device 110 by typing it on a keyboard or other inputdevice (not shown). Merchandising card data may also be enteredautomatically, for example, by scanning or swiping the merchandisingcard on user device 110 or merchant device 120, or by taking a pictureof the merchandising card using an application that may be installed onuser device 110.

Financial service provider device 130 may store acquired merchandisingcard data in memory 230 (step 340). For example, financial serviceprovider device 130 may store the acquired merchandising card data inclient data 234, in relation to the account identified in step 320.Additionally or alternatively, financial service provider device 130 maystore the acquired merchandising card data in database 240 and/or cloudservice 250. Financial service provider device 130 may associatemerchandising card data stored in database 240 and/or cloud service 250with the customer account identified in step 320. Associating theacquired merchandising card data with the customer account identified instep 230 may be accomplished, for example, by linking the merchandisingcard data with the customer account or by creating a subcategory ofmemory within the customer account for storing merchandising card datasuch as that acquired by financial service provider device 130 in step330.

FIG. 4 shows an exemplary process for managing merchandising cardreminders associated with a financial account, consistent with disclosedembodiments. At step 410, financial service provider device 130 maydetermine whether the user is located at a merchant location. In someembodiments, financial service provider device 130 may acquire anotification from merchant device 120 when the user presents a creditcard associated with a financial service provider and/or financialservice device 130 for payment via merchant device 120. In someinstances, the notification may occur automatically as a result ofdetection of the proximity of user device 110 to the merchant location.In certain embodiments, merchant device 120 may include one or moreservers that host a website. Thus, merchant device 120 may send anotification, indicating that the user is located at a merchantlocation, to financial service provider device 130 when user device 110sends a request to merchant device 120 via the website.

In certain embodiments, financial service provider device 130 mayacquire a notification from user device 110 when the user of user device110 has manually sent a notification (e.g., via a text, voice, email,social media message, interaction or gesture transmitted from a user touser device 110, etc.) to financial service provider device 130 that thecustomer is at the merchant location. In certain embodiments, financialservice provider device 130 may determine that a user is located at amerchant by determining that a merchandising card, which may beassociated with the user and financial service provider device 130, isswiped or used for payment at merchant device 120. In some embodiments,step 410 may be implemented using a process similar to the one in FIG.5, consistent with disclosed embodiments.

In accordance with FIG. 5, at step 510, financial service providerdevice 130 may acquire one or more locations associated with user device110 (i.e., device locations) over WAN 140 and/or local network 145. Insome embodiments, financial service provider device 130 may acquire thedevice locations in the form of GPS coordinates from a GPS unit, such asa GPS unit within user device 110. In some of these embodiments, anapplication installed in user device 110 may use a GPS function on userdevice 110 to transmit, via WAN 140 and/or local network 145, GPScoordinates to financial service provider device 130. Financial serviceprovider device 130 may acquire the locations at different instances intime within a predetermined period of time. For example, financialservice provider device 130 may acquire a set of GPS coordinates atfive-second intervals for five minutes, or, as another example, acquirea set of GPS coordinates at random intervals over a random period oftime based on a randomized equation. One of ordinary skill in the artwould understand that there are multiple configurations that financialservice provider device 130 may use to acquire one or more devicelocations at different instances in time within a predetermined periodof time.

At step 520, financial service provider device 130 may calculate anoverall merchant confidence rating. An overall merchant confidencerating may be represented in multiple ways. For example, an overallmerchant confidence rating may be represented by one or more numbers,symbols, words, or the like, or any combination thereof, as well as byindicators, such as “low,” “medium,” “high,” or the like.

In some embodiments, financial service provider device 130 may calculatean overall merchant confidence rating based on computing one or moreindividual merchant confidence ratings. In some embodiments, the overallmerchant confidence rating and/or one or more individual merchantconfidence ratings may be determined based on computing the ratingsduring a predetermined period of time. In some embodiments, financialservice provider device 130 may implement step 520 using a process shownin FIG. 6, consistent with disclosed embodiments.

In FIG. 6, at step 610, financial service provider device 130 maydetermine a first individual merchant confidence rating that may bebased on whether the user device locations are within a geofence. Forexample, financial service provider device 130 may determine a geofence,that is, one or more vertices and/or points surrounding a geographicarea, that is associated with a merchant location. In certainembodiments, financial service provider device 130 may look upcoordinates by using one or more device locations (acquired in step510), database 240, and/or cloud service 250. For example, financialservice provider device 130 may look up vertices that define theboundary of a geofence associated with a merchant location; points thatdefine the boundary of a geofence associated with a merchant location;an equation that defines the boundary of a geofence associated with amerchant location; or the like; or any combination thereof. In certainembodiments, financial service provider device 130 may determine ageofence that is associated with a merchant location by using anapplication programmable interface (API).

After financial service provider device 130 has determined a geofencethat is associated with a merchant location, financial service providerdevice 130 may then determine whether the device locations (acquired instep 510) associated with user device 110 are within the geofence. Insome embodiments, financial service provider device 130 may not requireall the device locations to be within the geofence, but may require onlythat a predetermined number or percentage of the device locations arewithin the geofence. In some embodiments, if less than a predeterminednumber or percentage of the device locations are within the geofence,financial service provider device 130 may acquire additional devicelocations. In some embodiments, the financial service provider maydetermine a higher first individual merchant confidence rating based ondetecting that user device 110 has been in the geofence for a longerpredetermined period of time.

In certain embodiments, financial service provider device 130 maydetermine that the first individual merchant confidence rating isdirectly proportional to the number of device locations within thegeofence. In other words, financial service provider device 130 maydetermine a higher merchant confidence rating based on a higher numberof device locations existing within the geofence. In some embodiments,financial service provider device 130 provider may determine, forexample, that if the device locations are less than the predeterminednumber or percentage of the device locations, then the first individualmerchant confidence rating is lower than a different first individualmerchant confidence rating determined when the device locations aregreater than or equal to the predetermined number or percentage of thedevice locations.

At step 620, financial service provider device 130 may determine asecond individual merchant confidence rating that is based on detectingmotion of user device 110 using, for example, device locations. Forexample, financial service provider device 130 may detect a motion ofuser device 110 by determining that a displacement exists between atleast two of the device locations. In some embodiments, financialservice provider device 130 may only detect motion when the displacementis above a predetermined threshold.

In certain embodiments, financial service provider device 130 maydetermine a higher second individual merchant confidence rating if thedetected motion or the displacement between two or more consecutive(i.e., consecutively acquired in time) device locations are below apredetermined threshold. If the displacement is high or large, thenfinancial service provider device 130 may determine that the user hasmoved too far to be within a particular merchant location. For example,if the displacement between device locations is 50 yards, then it isunlikely that the user is actually inside or in proximity to a merchantlocation of a small retailer on a block in New York City, N.Y. However,if the merchant is a football team and the merchant location is afootball stadium, financial service provider device 130 may determine ahigher second merchant confidence rating even if the displace of a useris 50 yards (described with the understanding that a football field isnormally at least 100 yards). Therefore, the second merchant confidencerating may be based on not only the motion of user device 110 but alsothe type of merchant and/or known details about the particular merchantlocation or surrounding the merchant location (e.g., perimeter of thelocation, shape of the location, area of the location, size of thelocation, etc.).

In some embodiments, financial service provider device 130 may determinea confidence rating only when there is little to no displacement betweensuccessive location determinations; in other words, financial serviceprovider device 130 may detect a stop. Financial service provider device130, in some embodiments, may determine a higher second individualmerchant confidence rating based on detecting that user device 110 hasbeen stopped for a longer predetermined period of time.

In certain embodiments, financial service provider device 130 maydetermine a higher second individual merchant confidence rating if thedetected motion or the displacement between consecutive device locationsis representative of a predetermined shopping pattern. For example,financial service provider device 130 may determine that a user wouldtypically move around within a merchant location (e.g., grocery store)in a predetermined shopping pattern or manner (e.g., fruits andvegetables aisle first, frozen foods aisle second, etc.), so financialservice provider device 130 may determine a second merchant rating thatis directly proportional to similarity of a pattern defined by thedevice locations to a predetermined shopping pattern. For example,financial service provider device 130 may determine a higher secondindividual merchant confidence rating if the device locations pattern isvery similar to the predetermined shopping pattern.

At step 630, financial service provider device 130 may determine a thirdindividual merchant confidence rating that is based on detecting amotion characteristic of user device 110. A motion characteristic mayinclude speed, acceleration, rotational speed, rotational acceleration,momentum, force, or the like that could be calculated using the devicelocations, the mass of the device, time, etc., by one of ordinary skillin the art.

In some embodiments, financial service provider device 130 may detectthe motion characteristic of user device 110 using device locations(acquired in step 510). For example, financial service provider device130 may detect a motion characteristic of user device 110 by determiningthat there is a displacement between at least two of the devicelocations over a certain time period. In some embodiments, financialservice provider device 130 may only detect a motion characteristic whenthe displacement is above a predetermined threshold. In someembodiments, financial service provider device 130 may determine ahigher third individual merchant confidence rating based on detectingthat user device 110 has a little to none of a motion characteristic(e.g., similar to detecting a stop) for a predetermined period of time.

In certain embodiments, financial service provider device 130 maydetermine a higher third individual merchant confidence rating if thedetected a motion characteristic is below a predetermined threshold. Forexample, using speed as the motion characteristic, financial serviceprovider device 130 may determine that speeds above regular walkingand/or running speeds indicate that a user is not inside or in proximityto a merchant location. Instead, financial service provider device 130may determine that the user or device is inside of a vehicle, such as anautomobile, airplane, or the like. In some embodiments, financialservice provider device 130 may determine the third individual merchantconfidence rating based on not only the device location but also on theparticular merchant or merchant location. For example, if the merchantis an airline company, financial service provider device 130 maydetermine that a higher speed is associated with a high merchantconfidence rating or may disregard the speed because financial serviceprovider device 130 may determine that the user is in an airplanebelonging to the merchant. In some embodiment, however, if the merchantis a grocery store, financial service provider device 130 may determinea lower speed (e.g., normal walking/running speed) is associated with ahigher merchant confidence rating.

Similar to step 620, financial service provider device 130 may determinea higher third individual merchant confidence rating if the detectedmotion characteristics are representative of predetermined shoppingmotion characteristics. For example, using speed as the motioncharacteristic, financial service provider device 130 may determine thata user would typically move around a merchant (e.g., car wash) at apredetermined speed (e.g., five minutes to wash, ten minutes to wax, twominutes to dry, etc.), so financial service provider device 130 maydetermine a third merchant rating that is directly proportional tocloseness of a speed that the device locations of user device 110creates and the predetermined shopping speed. For example, financialservice provider device 130 may determine a higher third individualmerchant confidence rating if the speed that the device locations creatematches the predetermined shopping speed more closely.

At step 640, financial service provider device 130 may determineadditional individual merchant confidence ratings. In some embodiments,financial service provider device 130 may determine an individualmerchant confidence rating based on detecting a significant change inlocation using the device locations. In some embodiments, financialservice provider device 130 may determine an individual merchantconfidence rating that is higher if the device locations have notchanged significantly or are within a predetermined range of each other.Financial service provider device 130 may determine that a user has lefta location if there is a significant change or if one or more of thedevice locations are not within a predetermined range of the otherdevice locations.

Moreover, in some embodiments, financial service provider device 130 maydetermine an individual merchant confidence rating based on otherfactors not associated with the device locations. For example, in someembodiments, financial service provider device 130 may determine anindividual merchant confidence rating based on whether a user device 110is connected to a local network 145 that is associated with a merchantlocation. For example, financial service provider device 130 may causeuser device 110 to send the name of local network 145 (e.g., a Wi-FiSSID, or the like) that is connected to user device 110. Financialservice provider device 130 may then use database 240 and/or cloudservice 250 to look up one or more names of the networks associated witha merchant location and determine if the name of local network 145acquired from user device 110 matches one of the one or more names ofthe networks associated with the merchant location. In some embodiments,if the name of local network 145 acquired from user device 110 matchesone of the one or more names of the networks associated with themerchant location, financial service provider device 130 may determine ahigher individual merchant confidence rating than if the merchantconfidence ratings did not match. Moreover, in some embodiments wherefinancial service provider device 130 determines that the name of localnetwork 145 acquired from user device 110 matches one of the one or morenames of the networks associated with the merchant location, financialservice provider device 130 may determine a higher merchant confidencerating if the name of local network 145 acquired from user device 110matches a particular name of a network that is associated with themerchant location. For example, the one or more names of the networksassociated with the merchant location may be ranked by, for example,signal strength and/or frequency of use, so financial service providerdevice 130 may determine a higher merchant confidence rating if the nameof local network 145 acquired from user device 110 matches a higherranked name of a network that is associated with the merchant location.

At step 650, financial service provider device 130 may calculate anoverall merchant confidence rating based on one or more of theindividual merchant confidence ratings. In certain embodiments,financial service provider device 130 may use one or more individualmerchant confidence ratings and one or more formulas, comparisons, orthe like, or any combination thereof to calculate the overall merchantconfidence rating. For example, financial service provider device 130may input two or more individual merchant confidence ratings into aweighted average formula to calculate the overall merchant confidencerating. As another example, financial service provider device 130 maynormalize the individual merchant confidence ratings to calculate theoverall merchant confidence rating. Even further, as another example,financial service provider device 130 may compare two or more individualmerchant confidence ratings in a particular order and/or a particularway to calculate the overall confidence ratings. In certain embodiments,financial service provider device 130 may use an API to calculate theoverall merchant confidence rating and/or the individual merchantconfidence ratings.

Returning now to FIG. 5, at 530, financial service provider device 130may determine whether the overall merchant confidence rating is greaterthan or equal to a first predetermined threshold. For example, in someembodiments, the first predetermined threshold may be a medium or highrating. In some embodiments, if financial service provider device 130determines that the overall merchant confidence rating is not greaterthan or equal to the first predetermined threshold, then financialservice provider device 130 may determine whether the overall merchantconfidence rating is greater than or equal to a second predeterminedthreshold (at step 540). For example, in some embodiments, the secondpredetermined threshold may be a low or medium rating. In someembodiments, if financial service provider device 130 determines thatthe overall merchant confidence rating is not greater than or equal tothe first predetermined threshold, financial service provider may startover and acquire more device locations (at step 510) or determine thatthe user is not at the merchant (step 410: no).

In some embodiments, if financial service provider device 130 determinesthat the overall merchant confidence rating is greater than or equal tothe first predetermined threshold (step 540: yes), financial serviceprovider device 130 may recalculate the overall merchant confidencerating using a different set of individual merchant confidence ratings(steps 610-650). In certain embodiments, financial service providerdevice 130 may, alternatively or additionally, use other methods (notdiscussed in steps 610-650) to recalculate the overall merchantconfidence rating. For example, financial service provider device 130may use historical hit-or-miss (success or failure) rates associatedwith past determinations of whether a device was at a merchant locationand/or other data points (e.g., merchant, merchant location, type ofuser device, and other parameters associated with the user and/ormerchant environment) to recalculate the merchant confidence ratingusing machine learning. In certain embodiments, financial serviceprovider device 130 may use the historic hit-or-miss rates and/or otherdata to train a confidence (i.e., classification) model for machinelearning. In some embodiments, financial service provider device 130 maycalculate a higher overall confidence rating if there are more hitsassociated with the second predetermined threshold and/or other datapoints. The various ways of determining overall and/or individualconfidence ratings, as described above, are only illustrative. One ofordinary skill in the art may use other techniques to determine overalland/or individual confidence ratings.

In some embodiments, once the second merchant confidence rating isrecalculated, financial service provider device 130 may determine, insome embodiments, if the recalculated overall merchant confidence ratingis greater than the first predetermined threshold (at step 560). Iffinancial service provider device 130 determines that the recalculatedoverall merchant confidence rating is not greater than the firstpredetermined threshold (step 560: no), financial service providerdevice 130 may, in some embodiments, start over and acquire more devicelocations (at step 510) or determine that the user is not at themerchant (step 410: no). On the other hand, in some embodiments, iffinancial service provider device 130 determines that the recalculatedoverall merchant confidence rating is greater than the firstpredetermined threshold, financial service provider device 130 maydetermine that the user is at the merchant (step 410: yes).

Returning now to FIG. 4, if financial service provider device 130determines that the user is located at a merchant location, at step 420,financial service provider device 130 may determine whether a merchant,associated with the merchant location where the user is located, matchesa merchant that is associated with a merchandising card (e.g., acquiredin step 330 and stored in step 340). In some embodiments, financialservice provider device 130 may execute a process of FIG. 7 to determinewhether a merchant, associated with the merchant location where the useris located, matches a merchant that is associated with a merchandisingcard.

In accordance with FIG. 7, at step 710, financial service providerdevice 130 may acquire one or more merchant identifiers (e.g., merchantnames) that are associated with a merchant location where the user islocated. For example, financial service provider device 130 may acquirea merchant identifier that is associated with a merchant location wherethe user is located by using an API, database 240, cloud service 250,outside resource, and/or one or more of the device locations.

At step 720, financial service provider device 130 may acquire one ormore merchant identifiers that are associated with a merchandising card.For example, financial service provider device 130 may acquire amerchant identifier that is associated with a merchandising card from anAPI, database 240, cloud service 250, outside resource, and/or one ormore of the device locations.

Returning again to FIG. 4, in some embodiments, at step 420, financialservice provider device 130 may determine whether the merchantidentifier (acquired at step 710) matches or is associated with themerchant identifier (acquired at step 720). In some embodiments, iffinancial service provider device 130 determines that the merchantidentifier acquired at step 710 matches or is associated with themerchant identifier acquired at step 720, financial service providerdevice 130 may determine that a merchant associated with the merchantlocation where the user is located, matches a merchant that isassociated with a merchandising card (step 420: yes).

At step 430, financial service provider device 130 may send a reminder(i.e., notification) to user device 110. The reminder may indicateinformation associated with the merchandising card, user, financialservice provider, merchant, user device 110, merchant device 120,financial service provider device 130, or the like.

In some embodiments, financial service provider device 130 may send areminder using a text, email, voice, push notification, social mediamessage, or the like. The reminder may, in certain embodiments, includea message indicating that the user is a holder of a merchandising cardassociated with the merchant and/or merchant location. In someembodiments, financial service provider device 130 may cause user device110 to display a reminder. The displayed reminder may include an imagerepresentative of a merchandising card. In some embodiments, thedisplayed reminder may include images representing the front, bank,and/or side of the merchandising card. The images may be acquired, forexample, from an API, database 240, an outside resource, and/or cloudservice 250. In some embodiments, financial service provider device 130may provide to user 110, and/or cause user device 110 to display, a linkassociated with a merchandising card.

At step 440, financial service provider device 130 may acquire anactivation request from a user interacting with the reminder. In someembodiments, financial service provider device 130 may acquire anactivation request when there is an interaction with or a selection ofthe link. An interaction may include, for example, any gesture that canbe detected by user device 110 to communicate with user device 110. Agesture may include, for example, a touch, tap, click, wave, press,sound, movement of a body part, or the like.

At step 450, financial service provider device 130 may display an imagerepresenting the front, bank, and/or side of the merchandising card. Forexample, in some embodiments, financial service provider device 130 maycause user device 110 to display the image. At step 460, financialservice provider device 130 may prepare the merchandising card to beused at merchant device 120. For example, financial service providerdevice 130 may cause user device 110 to prepare the merchandising cardto be used at merchant device 120 by, for example, causing user device110 to transmit data associated with merchandising card to merchantdevice 120 (e.g., via a near-field communication, radio frequencyidentification, magnetic secure transmission, WAN 140, local network145, etc.)

It should be understood that, although FIGS. 4-7 are described as beingperformed by financial service provider device 130, one or more othercomponents of system 100 may perform any or all steps of FIG. 4-7. Forexample, the steps may be performed exclusively or in combination withan application installed on user device 110, merchant device 120, and/orfinancial service provider device 130.

In some embodiments, some or all of the logic for the above-describedtechniques may be implemented as a computer program or application or asa plug-in module or sub-component of another application. The describedtechniques may be varied and are not limited to the examples ordescriptions provided. In some examples applications may be developedfor download to mobile communications and computing devices, e.g.,laptops, mobile computers, tablet computers, smartphones, etc., beingmade available for download by the customer either directly from thedevice or through a website.

Moreover, while illustrative embodiments have been described herein, thescope thereof includes any and all embodiments having equivalentelements, modifications, omissions, combinations (e.g., of aspectsacross various embodiments), adaptations and/or alterations as would beappreciated by those in the art based on the present disclosure. Forexample, the number and orientation of components shown in the exemplarysystems may be modified. Further, with respect to the exemplary methodsillustrated in the attached drawings, the order and sequence of stepsmay be modified, and steps may be added or deleted.

Thus, the foregoing description has been presented for purposes ofillustration. It is not exhaustive and is not limiting to the preciseforms or embodiments disclosed. Modifications and adaptations will beapparent to those skilled in the art from consideration of thespecification and practice of the disclosed embodiments. For example,while a financial service provider has been described herein as theentity generating, providing, managing, and/or maintaining themerchandising card management program for one or more customers, it isto be understood that, consistent with disclosed embodiments, anotherentity may provide such services in conjunction with or separate from afinancial service provider.

The claims are to be interpreted broadly based on the language employedin the claims and not limited to examples described in the presentspecification. Accordingly, the examples presented herein are to beconstrued as non-exclusive. Further, the steps of the disclosed methodsmay be modified in any manner, including by reordering steps and/orinserting or deleting steps.

Furthermore, although aspects of the disclosed embodiments are describedas being associated with data stored in memory and other tangiblecomputer-readable storage mediums, one skilled in the art willappreciate that these aspects can also be stored on and executed frommany types of tangible computer-readable media, such as secondarystorage devices, like hard disks, floppy disks, or CD-ROM, or otherforms of RAM or ROM. Accordingly, the disclosed embodiments are notlimited to the above-described examples but, instead, are defined by theappended claims in light of their full scope of equivalents.

What is claimed is:
 1. A method for providing mobile devicenotifications, the method comprising: acquiring, from a mobile deviceover a network, a plurality of device locations associated with themobile device at different instances in time, the device locations beingdetermined based on at least one of a global positioning system (GPS) ofthe mobile device or a network location; determining co-location at afirst merchant by: determining a geofence associated with a physicallocation based on points surrounding a geographic area associated withthe physical location; calculating a merchant confidence value based ona first rating and a second rating, the first rating being proportionalto a number of device locations inside the geofence within apredetermined time period, the second rating being inverselyproportional to a movement between the plurality of device locations;recalculating the merchant confidence value using a machine learningmodel trained with historic hit-or-miss rates associated with pastdeterminations; and determining the recalculated confidence is above athreshold; upon determining co-location at the first merchant,determining whether the first merchant is associated with amerchandising account associated with the mobile device; and upondetermining that the first merchant is associated with a merchandisingaccount associated with the mobile device: sending a notification to themobile device; acquiring an activation request from a user of the mobiledevice, the activation request being generated in response to the userinteracting with the notification; and configuring a setting of themobile device to prepare the merchandising account for use at thephysical location.
 2. The method of claim 1, wherein determining whetherthe first merchant is associated with the merchandising accountcomprises: acquiring a first merchant identifier associated with thefirst merchant; acquiring a plurality of available merchant identifiers,the available merchant identifiers being associated with merchandisingaccounts associated with the mobile device; and determining whether thefirst merchant identifier matches at least one of the available merchantidentifiers.
 3. The method of claim 2, wherein at least one of theplurality of available merchant identifiers comprises a merchantidentifier associated with a user location.
 4. The method of claim 2,wherein at least one of the plurality of available merchant identifiersis associated with a merchant category code.
 5. The method of claim 1,wherein the notification comprises at least one of a push notification,a text message, an email, or a social media message.
 6. The method ofclaim 1, wherein the notification comprises an image representative of amerchandising card associated with the merchandising account, the imagecomprising at least one of a first image representing the front of themerchandising card or a second image representing the back of themerchandising card.
 7. The method of claim 1, wherein: determiningco-location at the first merchant further comprises determining theco-location based on at least one of: a speed detected using the devicelocations over the predetermined time period; or a movement pattern ofthe mobile device over the predetermined time period based on devicelocation; and calculating the merchant confidence value comprisesadjusting the merchant confidence value based on a third rating, thethird rating being determined based on a motion characteristic of thedevice locations.
 8. The method of claim 6, wherein: the notificationcomprises a link associated with the merchandising card; and the link,upon selection by the user, sends an activation request from the user.9. The method of claim 6, wherein the merchandising card comprises atleast one of a gift card, a loyalty card, a rewards card, or a discountcard.
 10. The method of claim 1, further comprising: determining whetherthe first rating is less than a first threshold, the first thresholdbeing proportional to a threshold number of device locations inside thegeofence within the predetermined time period; upon determining that thefirst rating is less than the first threshold, determining whether thefirst rating is greater than or equal to a second threshold; upondetermining that the first rating is greater than or equal to the secondthreshold: recomputing the first rating based on a confidence modelbased on the machine learning algorithm model and a plurality ofhistorical confidence ratings; and determining whether the recalculatedfirst rating is greater than or equal to the first threshold; upondetermining that the recalculated first rating is greater than or equalto the first threshold, determining co-location at the first merchantbased on the first rating.
 11. A system for providing mobile devicenotifications, the system comprising: one or more memory devices storinginstructions; and one or more processors configured to executeinstructions to perform operations comprising: acquiring, from a mobiledevice over a network, a plurality of device locations associated withthe mobile device at different instances in time, the device locationsbeing determined based on at least one of a global positioning system(GPS) of the mobile device or a network location; determiningco-location at a first merchant by: determining a geofence associatedwith a physical location based on points surrounding a geographic areaassociated with the physical location; calculating a merchant confidencevalue based on a first rating and a second rating, the first ratingbeing proportional to a number of device locations inside the geofencewithin a predetermined time period, the second rating being inverselyproportional to a movement between the plurality of device locations;recalculating the merchant confidence value using a machine learningmodel trained with historic hit-or-miss rates associated with pastdeterminations; and determining the recalculated confidence is above athreshold; upon determining co-location at the first merchant,determining whether the first merchant is associated with amerchandising account associated with the mobile device; and upondetermining that the first merchant is associated with a merchandisingaccount associated with the mobile device: sending a notification to themobile device; acquiring an activation request from a user of the mobiledevice, the activation request being generated in response to the userinteracting with the notification; and configuring a setting of themobile device to prepare the merchandising account for use at the firstmerchant.
 12. The system of claim 11, wherein determining whether thefirst merchant is associated with the merchandising card comprises:acquiring a first merchant identifier associated with the firstmerchant; acquiring a plurality of available merchant identifiers, theavailable merchant identifiers being associated with merchandisingaccounts associated with the mobile device; and determining whether thefirst merchant identifier matches one of the available merchantidentifiers.
 13. The system of claim 12, wherein at least one of theplurality of available merchant identifiers comprises a merchantidentifier associated with a user location.
 14. The system of claim 12,wherein at least one of the plurality of available merchant identifiersis associated with a merchant category code.
 15. The system of claim 11,wherein the notification comprises at least one of a push notification,a text message, an email, or a social media message.
 16. The system ofclaim 11, wherein the notification comprises an image representative ofa merchandising card associated with the merchandizing account, theimage comprising at least one of a first image representing the front ofthe merchandising card or a second image representing the back of themerchandising card.
 17. The system of claim 11, wherein: determiningco-location at the first merchant further comprises determining theco-location based on at least one of: a speed detected using the devicelocations over the predetermined time period; or a movement pattern ofthe mobile device over the predetermined time period based on devicelocation; and calculating the merchant confidence value comprisesadjusting the merchant confidence value based on a third rating, thethird rating being determined based on a motion characteristic of thedevice locations.
 18. The system of claim 16, wherein: the notificationcomprises a link associated with the merchandising card; and the link,upon selection by the user, sends an activation request from the user.19. The system of claim 16, wherein the merchandising card comprises atleast one of a gift card, a loyalty card, a rewards card, or a discountcard.
 20. The system of claim 11, further comprising: determiningwhether the first rating is less than a first threshold, the firstthreshold being proportional to a threshold number of device locationsinside the geofence within the predetermined time period; upondetermining that the first rating is less than the first threshold,determining whether the first rating is greater than or equal to asecond threshold; upon determining that the first rating is greater thanor equal to the second threshold: recomputing the first rating based ona confidence model based on the machine learning algorithm model and aplurality of historical confidence ratings; and determining whether therecalculated first rating is greater than or equal to the firstthreshold; and upon determining that the recalculated first rating isgreater than or equal to the first threshold, determining co-location atthe first merchant based on the first rating.